Conversation
03_configure_undercloud.sh
Outdated
| openstack flavor create --ram 1024 --disk 10 --vcpu 2 --public tiny | ||
| openstack flavor create --ram 10240 --disk 20 --vcpu 2 --public m1.medium | ||
| openstack flavor create --ram 8192 --disk 20 --vcpu 2 --public m1.medium | ||
| openstack network create --external --provider-physical-network datacentre --provider-network-type flat public |
There was a problem hiding this comment.
The commit message says 4096 but the change is 8192?
There was a problem hiding this comment.
Oops. I guess I ammended the commit message but forgot to include the actual change.
I started with 8192, as that matches the AWS flavor in use, but that wasn't actually small enough to work in my test env.
A better solution here is making flavor a deployment choice, and i've got an installer patch in progress to add that. I still think 4096 is probably a kinder default though.
There was a problem hiding this comment.
4 GB is now the libvirt default - https://github.com/openshift/installer/pull/785/files
m1.medium was created with 10240 MB of RAM. Change this to 4096 to be more dev env friendly. AWS uses a flavor with 8 GB by default (m4.large), but the libvirt provider is using 2 and 3 GB VMs, so 4 GB should be enough. We may just need to make flavor selection easier.
hardys
left a comment
hardys
left a comment
There was a problem hiding this comment.
lgtm, I've been testing locally with as little as 2G and coreos will boot so 4G should be a reasonable default I think
|
related, added flavor selection support here: openshift/installer#788 |
|
Once we've got the flavor selection merged, could we create multiple flavours here and default to the 8GB one? I'm sympathetic to the low-mem users, but for a default I'd like to stick with what AWS has. |
In that case should we just make the number a variable, defaulted to $whatever, then folks can set whatever they want in their CONFIG file? |
|
A variable makes sense for now. I’ll update this.
I’ll also rework this later when flavor selection lands.
On Thu, Dec 6, 2018 at 5:12 AM Steven Hardy ***@***.***> wrote:
Once we've got the flavor selection merged, could we create multiple
flavours here and default to the 8GB one? I'm sympathetic to the low-mem
users, but for a default I'd like to stick with what AWS has.
In that case should we just make the number a variable, defaulted to
$whatever, then folks can set whatever they want in their CONFIG file?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#18 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAS4CrJyntbk9qPh97lQgfzHARte1nAMks5u2O2HgaJpZM4Y_Pqj>
.
--
Russell Bryant
|
| fi | ||
| if ! openstack flavor show m1.medium; then | ||
| openstack flavor create --ram 10240 --disk 20 --vcpu 2 --public m1.medium | ||
| openstack flavor create --ram 4096 --disk 20 --vcpu 2 --public m1.medium |
There was a problem hiding this comment.
whaaaaaaaaaaaaaaaaaaaaat? Don't you like wasting resources? 😄
4 participants
m1.medium was created with 10240 MB of RAM. Change this to 8192,
which matches what is being used on AWS (m4.large).